Systems and methods for controlling delivery of user messages

ABSTRACT

Systems and methods for determining whether to send a message to a user take into account a pressure score for the user that is indicative of how receptive the user is to receiving messages. The user&#39;s pressure score can vary depending on user behavior. Multiple pressure scores relating to different respective topics or subjects may be maintained for the user.

This application is a continuation of U.S. application Ser. No.16/255,254, which was filed on Jan. 23, 2019, the content of which ishereby incorporated by reference.

BACKGROUND OF THE INVENTION

The invention is related to systems and methods for enhancing customerengagement. In part, enhanced customer engagement is accomplished by acompany sending messages to its users. The messages could be mobile orbrowser-based push notifications, text (SMS/MMS) messages, emailmessages, in-app messages, an audio recording that is sent to users viaa telephony system, or some other form of messaging.

A company may directly send a message to its users, or the company mayhire a vendor to send a message to its users. If an outside vendor isused, the company typically will provide the content of the message, andthe company will identify which users are to receive the message.

The users who receive a message from a company tend to have differentattitudes towards receiving such a message. Different users havedifferent propensities to derive value from the message. As a result,some users will welcome the message and immediately read/play themessage, while other users may ignore the message completely.

It is difficult for a company sending such messages, or for an outsidevendor responsible for sending such messages on behalf of the company,to know in advance whether an individual user is likely to be receptiveto a message. Indeed, an outside vendor is unlikely to have any detailedinformation regarding the preferences and characteristics of individualusers. For that reason, most companies will send a message to all oftheir users, or at least to all of their users that might potentiallyfind value in the message. Unfortunately, by operating in this fashionthe company runs the risk of alienating certain users that find themessage unwelcome. If a company repeatedly sends messages to a user whodoes not want to receive messages or who finds little or no value in thecompany's messages, the user may discontinue any affiliation with thecompany.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a communications environment which could beutilized by systems embodying the invention to perform methods embodyingthe invention;

FIG. 2 is a diagram illustrating selected elements of a customerengagement platform;

FIG. 3 is a diagram illustrating selected elements of a pressure scoreunit that can be part of a customer engagement platform;

FIG. 4 is a flowchart illustrating steps of a first method embodying theinvention;

FIG. 5 is a flowchart illustrating steps of a second method embodyingthe invention;

FIG. 6 is a flowchart illustrating steps of a third method embodying theinvention; and

FIG. 7 is a diagram of a computer system and associated peripheralswhich could embody the invention, or which could be used to practicemethods embodying the invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of preferred embodiments refers tothe accompanying drawings, which illustrate specific embodiments of theinvention. Other embodiments having different structures and operationsdo not depart from the scope of the present invention.

Systems and methods embodying the invention can be part of a customerengagement service. The customer engagement service helps a companyinteract with its users to enhance the customer experience and toincrease the company's business, revenue and/or stature. One of the waysthat a customer engagement service assists a company is by helping thecompany manage how and when messages are delivered to the company'scustomers. Details about how a customer engagement service operates areprovided below.

The following description refers to “clients” and to “users”. Forpurposes of this discussion, a “client” would be a client of thecustomer engagement service. In other words, a company or business thatis being assisted by the customer engagement service. “Users” are aclient's users, not users of the customer engagement service. Thecustomer engagement service sits between a client and the client's usersto manage and orchestrate the delivery of messages sent from the clientto its users.

A “message” could take many different forms and be delivered to a userin many different ways. For example, a “message” could be a mobile orbrowser-based push notification sent to users by a push notificationservice.

A message could also be an in-app message that is delivered to a uservia a software application. Often the software application is onecreated by the client company and provided to the client's users. Thesoftware application could be one that is resident on a computer, asmartphone or any other device with a processor that is capable ofrunning such a software application. The in-app messages generatedand/or delivered by such a software application could be received by theuser in various ways.

A message also could be a text message (SMS/MMS) that is delivered tousers via a smartphone or via a text messaging software application. Amessage also could be a message delivered to a user via a social mediaservice, or via an Over The Top (OTT) messaging service. A message alsocould be an email message that is delivered to users via standard emailservice providers. Moreover, a message could be an audio messagedelivered to a user via a telephony or VOIP service provider, or a videomessage delivered via similar means.

For purposes of the following description and the appended claims, anyreference to sending a “message” to users is intended to encompass anyof the different types of messages and delivery channels mentionedabove, as well as any message types and delivery means that aredeveloped in the future.

A customer engagement service embodying the invention is similar to atraditional message delivery service in certain limited respects. Forexample, a client could ask a customer engagement service to send amessage to its users just as it might ask a message delivery service tosend a message to its users. However, unlike a traditional messagedelivery service, a customer engagement service actively manages andorchestrates how the message is delivered to users. In addition, in manycases the customer engagement service does not actually send themessage, as would a traditional message delivery service. Instead, themessage delivery service manages the delivery of the message to usersvia third party message delivery services.

In addition, and for reasons that will be explained below, a customerengagement service typically has considerably more information about theusers and the users' behavior than would be available to a typicalmessage delivery service. This additional information is used to helpmanage, control and orchestrate the delivery of a client's message tomultiple users to achieve various purposes.

Systems and methods embodying the invention are designed to limit orcontrol the delivery of messages to a user in instances where thecustomer engagement service detects or infers that the user may not bereceptive to messages. The aim is to improve an individual user'soverall experience by reducing or preventing the delivery of messages tothe user that the user may not find useful or interesting, or that theuser may not welcome.

In some instances, the customer engagement service may limit or reducethe delivery of messages to a user when the messages relate to aparticular topic or subject. This is done because information about theuser, including past actions taken by the user, indicate that the usermay not be receptive to messages relating to that topic or subject.

In other instances, the customer engagement service may limit or reducethe delivery of a certain type of message to a user. For example, thecustomer engagement service may reduce or limit the number of textmessages that are sent to a user, while simultaneously allowing a normalflow of push notifications to be sent to the user. This would be donebecause information about the user, including past actions taken by theuser, indicate that the user is not receptive to text messages, butwelcomes push notifications.

As will be explained below, a customer engagement service embodying theinvention is able to gather more information about users' preferencesand activity than a traditional message delivery service. Thatinformation can be used to help determine whether a user is notpresently receptive to a certain client's messages, to determine whetherthe user is not receptive to messages relating to a particular topic orsubject and/or to determine whether the user is not receptive to certaintypes of messages.

In situations where the customer engagement service is managing andorchestrating the delivery of messages from multiple clients to the sameuser, the customer engagement service can use information about the howthe user reacts to messages sent from all of the clients to drawconclusions about the user's receptivity to messages in general, tomessages that relate to a certain topic or subject and/or to messages ofa certain type. Thus, the customer engagement service may have moreinformation about the user's preferences and receptivity to messagesthan any individual client. As a result, the customer engagement serviceis in a uniquely informed position to help manage the delivery ofmessages to the user to ensure the user has a positive experience.

FIG. 1 illustrates a communications environment in which a customerengagement service embodying the invention could exist. Beforeexplaining the details of the customer engagement service, we will firstdiscuss the communications environment.

As shown in FIG. 1, the communications environment includes client one30, client two 32 and the customer engagement service 50. Client one 30and client two 32 are clients of the customer engagement service 50. Theclients 30/32 can communicate with the customer engagement servicedirectly, via the Internet 22, or via other means.

Users of the clients 30/32 could utilize the clients' 30/32 services invarious ways. For example, if client one 30 is a media company thatprovides media content to its users, client one 30 could produce mediacontent that is sent via a broadcaster 20 to a client's television 10.That media content could be delivered to the user's television 10 via aset top box 12 that is connected to the user's television 10 and to theInternet 22 and/or a cable service provider 21. In some instances, asoftware application on the set top box 12 that is provided by clientone 30 could be used to deliver the content to the user's television 10.

The same or a different user might have a computer 14 that is connectedto the Internet 22. The user could utilize a web browser on the computer14 to access an Internet website provided by client one 30 that alsooffers media content. Similarly, a software application resident on theuser's computer 14 might also be used to access media content providedby client one 30 via the Internet 22.

Yet another user may have a smartphone 16 that is capable ofcommunicating over the Internet 22 and/or via a telephony serviceprovider 24. A software application on the user's smartphone 16 could beused to access media content provided by client one 30 via the Internet22 or via the telephony service provider 24.

Still another user might have a cellular telephone 18 that is capable ofreceiving text messages. This would allow the user of the cellulartelephone 18 to receive text messages from client one 30.

FIG. 1 also shows that a first push notification service (PNS) 40 and asecond push notification service 42 could be used by the customerengagement service 50 to deliver push notifications to smartphonesand/or web browsers. Such messages could be delivered by the pushnotification services 40/42 to user smartphones via the Internet 22 orvia a telephony service provider 24 that provides a user smartphone withits native telephony service.

FIG. 1 also shows that an email delivery service 44 could be used by thecustomer engagement service 50 to send email messages to users. Further,the customer engagement service 50 could use a text messaging service 46to send text messages to users, or an OTT messaging service 48 to sendformatted messages to users. Moreover, the customer engagement service50 might send a message to users via one or more social networkingservices 49. Of course, the customer engagement service 50 could utilizeany other message delivery service as well to communicate messages tousers.

The clients 30/32 in this communications environment could be any sortof client that utilizes a customer engagement service 50 to help themmanage engagement with their users. As noted above, a client could be amedia broadcaster that produces and sends media content to its users. Inother instances, a client could be a retailer whose purchasers are itsusers. In still other instances, the client could be a service provider,such as a telephony service provider or an Internet service provider.Virtually any business that wishes to send messages to its users couldbe a client in this environment.

One of skill in the art will appreciate that FIG. 1 only illustrates avery limited number of devices that could be utilized by users toreceive messages from a client, and that could be used to interact witha client. In reality, there would be a very large number of user devicesin such a communications environment. Also, a single user could possessand use multiple devices to access client services and to receivemessages from a client. Thus, the depiction in FIG. 1 should in no waybe considered limiting.

FIG. 2 illustrates selected elements of a customer engagement service50. The illustration in FIG. 2 is in no way intended to show allelements of a typical customer engagement service 50. Indeed, a typicalcustomer engagement service 50 would include many other elements.Likewise, a customer engagement service 50 embodying the invention mightnot have all the elements illustrated in FIG. 2.

The customer engagement service 50 includes a user information unit 210that is responsible for receiving and storing information about aclient's users. The user information unit 210 also responds to requestsfor the information stored within its databases. The user informationunit 210 includes a data receiving unit 212 that receives various itemsof information about users, and that stores that received information indatabases 214. The information could be received from various sources.However, typically, a client would provide information about its usersto the data receiving unit 212 via various means.

For example, in some instances a client may send notifications to thedata receiving unit 212 each time that one of the client's users engageswith the client in some fashion. For example, if the client is an onlineretailer, each time that a user makes a purchase from the onlineretailer, the online retailer could send information about that purchaseto the data receiving unit 212.

In another example, if the client is a media broadcaster, and one of themedia broadcaster's users logs onto a website provided by the mediabroadcaster to access media content, the media broadcaster could senddata about that contact to the data receiving unit 212. The data sentcould include an identification of the user, the time that the useraccessed the website and an indication of what the user accessed orwatched while logged into the website. Similarly, any time that a useraccesses a client's website, the client could automatically report thatuser activity to the data receiving unit 212 of the customer engagementservice 50.

In yet another example where the client is a media broadcaster, themedia broadcaster could have provided a software application to a userthat the user has loaded onto a smartphone or a computing device. Thesoftware application could be configured to report the actions that auser takes when using the software application directly to the datareceiving unit 212 of a customer engagement service 50. Indeed, in anyinstance where the client has provided a software application to itsusers, the software application could be configured to report useractivity to the data receiving unit 212 of the customer engagementservice 50.

The data receiving unit 212 may also receive information about howindividual users react to the receipt of client messages. If thecustomer engagement service 50 causes a push notification to be sent toa user via a push notification service 40/42, the push notificationservice 40/42 that sends the push notification to the user may reportwhether the user opened and viewed the push notification. That reportcan include the time at which the push notification was sent to theuser, and the time at which the user opened and viewed the pushnotification. This information could be reported to the data receivingunit 212, which then stores this information in the databases 214.

In a similar fashion, when the customer engagement service 50 sendsother types of messages to a user, such as text messages, email messagesor audio messages, the delivery service that sends the message to theuser can report back about when the message was sent, and whether andwhen the user opened and/or viewed and/or listened to the message. Ofcourse, information about whether and when a user opened or viewed amessage could be obtained by the user information unit 210 in otherways. The obtained information is then recorded in the databases 214.

In yet another example, the customer engagement service 50 may cause amessage to be delivered to a user via an in-application messagingcapability of a software application that was provided to the user by aclient. In that instance, the software application or the client thatprovided and monitors the software application may notify the customerengagement service 50 about when the message was delivered and whetherand when the user accessed and viewed the message. Here again, thereported information is recorded in the databases 214.

Because the customer engagement service 50 is able to obtain informationabout how individual users react to the messages they receive, thecustomer engagement service 50 can use this information to determine anindividual user's receptivity to messaging in general, to messages thatare directed to a particular topic or subject, and to messages of acertain type. The information can also indicate that a particular useris receptive to a first type of message during certain days and times,but is receptive to a second different type of message at other days andtimes.

The customer engagement service 50 may also receive information thatindicates whether and when the user takes an action in response toreceipt of a message. For example, because the data receiving unit 212is also receiving information from the clients regarding user contactswith the clients, the customer engagement service 50 may learn thatshortly after an individual user received a message from a client, theuser logged into the client's website. Or that shortly after the userreceived a message from a client, the user opened a software applicationprovided by the client.

For all the reasons outlined above, the customer engagement service 50is able to build detailed user profiles that can be used to predict howindividual users will act in certain situations, or how they willrespond to certain forms of messaging.

As shown in FIG. 2, the user information unit 210 also includes a queryunit 216. The query unit 216 queries the databases 214 to obtain variousitems of information about the users. The obtained information can beused to control and orchestrate the delivery of messages to users tohelp improve and control the user experience.

The customer engagement service 50 also includes a pressure score unit218. Details of the pressure score unit 218 are provided below. Briefly,the pressure score unit 218 maintains one or more pressure scores forindividual users. The pressure scores are used to predict how receptivea user will be to receipt of messages. Thus, pressure scores can be usedto help control or limit the delivery of messages to users to improvethe users' overall experience.

The customer engagement service 50 also includes a message sending unit220. The message sending unit 220 is responsible for causing messages tobe sent to a client's users. As explained above, messages could takemany different forms and have many different delivery channels. Themessage sending unit 220 includes a push notification sending unit 221that causes mobile or browser-based push notifications to be sent tousers via one or more push notification services 40/42, as illustratedin FIG. 1. The push notification sending unit 221 may obtain telephonenumbers and push notification service credentials for individual usersfrom the databases 214 with the assistance of the query unit 216.Alternatively, the client may provide that information to the messagesending unit 220. The user credential information is then used to causeone or more push notification services 40/42 to deliver a message to theusers.

The message sending unit 210 may also include a text message sendingunit 222 that causes text-based messages to be sent to users. Thetext-based messages could be traditional SMS/MMS messages, or messagesthat are delivered to users via an OTT messaging service or perhaps asocial networking service. Information needed to send such text-basedmessages to users may also be obtained from the databases 214 of theuser information unit 210, or that information may be provided by theclient. Here again, the message sending unit can enlist the services ofone or more text-based message delivery platforms to actually send themessage to users.

The message sending unit 220 may also include an email message sendingunit 224 that causes email messages to be sent to users. The emailmessage sending unit 224 may obtain email addresses and otherinformation, such as user names, for individual users from the databases214 with the assistance of the query unit 216, or that information maybe provided by the client. The information is then used to send emailmessages to users. The email messages may be delivered to users by oneor more third party email services.

The message sending unit 220 may also include a telephony sending unit226 that is responsible for delivering audio messages to users via atelephony system. For example, the telephony sending unit 226 couldgenerate an audio recording of a message that is to be delivered tousers, or the telephony sending unit 226 could receive such an audiomessage directly from the client. The telephony sending unit 226 wouldthen obtain information about individual customers from the databases214 with the assistance of the query unit 216, such as user telephonenumbers and user names, or that information could be provided by theclient. The telephony sending unit 226 would then enlist the aid of anoutside service to deliver the audio message to users via a traditionalor VOIP telephony system.

In some instances, the telephony sending unit 226 could generate andoperate interactive voice response (IVR) applications to deliver suchaudio messages to users. Doing so may allow a user to request andreceive information or services in addition to the original audiomessage. If a user does interact with an IVR application, how the userinteracts with the IVR application could also be recorded in thedatabases 214 as additional information about the user.

Regardless of the type of message or the delivery mechanism, the messagesending unit 220 could format the messages in ways specified by theclient, or in ways that the customer engagement service 50 believes willbe desirable or attractive to users. Also, the customer engagementservice 50 might itself be responsible for delivering the message tousers, or the customer engagement service 50 may utilize the services ofthird parties to deliver the message to users. In some instances,messages may be delivered to users via a combination of the customerengagement service 50 and outside vendors.

FIG. 3 illustrates selected elements of a pressure score unit 300. Asnoted above, the pressure score unit 300 maintains and updates one ormore pressure scores for individual users. As will be explained below,the pressure scores are used to help determine whether and when to sendmessages to an individual user, perhaps the type of message to send to auser, and/or when to limit the delivery of messages to an individualuser.

The pressure score unit 300 includes a pressure score maintenance unit302 that is responsible for maintaining and updating one or morepressure scores for individual users. Those pressure scores could bestored in databases 304 that are part of the pressure score maintenanceunit 302. Alternatively, some or all of the pressure scores could bestored in the databases 214 that are part of the user information unit210.

The pressure score unit 300 also includes a message threshold valuedetermining unit 306 that determines a message threshold value forindividual messages. As will be explained below, a user's pressurescore(s) and the message threshold value assigned to a message can beused to together to determine whether to send a message to a particularuser.

The pressure score unit 300 also includes a pressure score categorydetermining unit 308 that is responsible for determining that a messagebelongs to a particular category or subject or topic. The categoriesthemselves can vary widely depending on the client that is sending themessage.

For example, if the client is an online retailer, messages for thatclient could be categorized into product announcements, salenotifications, general user information, as well as other categories.The pressure scores that are maintained for the client's users couldinclude multiple pressure scores for each individual user, one pressurescore for each category of message. As a result, when the customerengagement service 50 is considering sending a message to this client'susers, the pressure category determining unit 308 may first examine themessage to determine into which category the message belongs. Then, foran individual user, a message send determining unit 310 of the pressurescore unit 300 will obtain or determine the pressure score for the userthat corresponds to that category. The message send determining unit 310then decides whether the message should be sent to that user based onthe user's pressure score for that category of message.

In another example, if the client is a media content provider, thecategories established for the client could be subject mattercategories. For example, the categories could be politics, sports andentertainment, as well as other categories. The pressure scores that aremaintained for this client's users could include multiple pressurescores for each user, one for each of the subject matter categories.When a message is to be sent for this client, the pressure categorydetermining unit 308 would first determine the subject matter categoryinto which the message falls. The message send determining unit 310would then use the pressure score for a user in that subject mattercategory to determine whether the message should be sent to the user.

With the above as background, we will now turn to a description ofvarious methods embodying the invention that relate to using pressurescores to control the delivery of messages to users. This description isprovided in conjunction with the flowchart illustrated in FIG. 4.

Perhaps the simplest situation is where a single pressure score ismaintained for each user. The single pressure score is then used todetermine whether to send a message to a user. Assuming that is thesituation, the method 400 would begin and proceed to step S402, wherethe customer engagement service 50 receives a message from a client thatis to be sent to some or all of the client's users. The instructionsreceived from the client may identify a candidate group of users towhich the message may be sent, or the client may indicate that thecandidate group of users includes all of the client's users. The clientthen relies upon the customer engagement service 50 to determine whoshould receive a copy of the message.

The method then proceeds to step S404, where the message senddetermining unit 310 obtains a pressure score for the first candidateuser. The method then proceeds to step S406 where the message senddetermining unit 310 determines if the message should be sent to thisuser. That determination is based on the user's pressure score.

As will be explained in greater detail below, a user's pressure score isindicative of how receptive the user is to receiving new messages. Inthe embodiments described below, a low pressure score indicates that theuser is more receptive to new messages, and a high pressure scoreindicates that the user is less receptive to new messages. Of course, inalternate embodiments this convention could be reversed such that a lowpressure score indicates a user is less receptive to new message andsuch that a high pressure score means that the user is more receptive tonew messages.

Once a user's pressure score is obtained in step S404, the methodproceeds to step S406, where a message send determining unit 310 usesthe user's pressure score to determine if the message should be sent tothe user. The determination made in step S406 could be as simple asdetermining if the user's pressure score is above or below a thresholdvalue. For example, the message send determining unit 310 could comparethe user's pressure score to a threshold value of 10. If the user'spressure score is equal to or lower than 10, then the message senddetermining unit 310 determines that the message should be sent to theuser. If the user's pressure score is greater than 10, the message senddetermining unit 310 determines that the message should not be sent tothe user.

If the determination made in step S406 is that the message should not besent to the user, the method proceeds to step S408, where a check isperformed to determine if all candidate users have been processed. Ifso, the method ends. If not, the method loops back to step S404, wherethe message send determining unit 310 obtains a pressure score for thenext user in the candidate list of users who might receive a copy of themessage. The method then proceeds on to step S406 and a determination ismade as to whether the message should be sent to the next user based onthe next user's pressure score.

If the check performed in step S406 indicates that the message should besent to a particular user, the method proceeds to step S410. In stepS410, the message sending unit 220 of the customer engagement service 50sends the message to that user. The method then proceeds to step S412,where a check is performed to determine if all candidate users have beenprocessed. If so, the method ends. If not, the method loops back to stepS404, where the message send determining unit 310 obtains a pressurescore for the next user on the candidate list of users who might receivethe message.

The method will continue looping through the above-described steps untila check performed in step S408 or S412 indicates that all candidateusers have been processed, and the method then ends.

In the method described above, only a single pressure score ismaintained for each user. In alternate methods, multiple pressure scoresmay be maintained for each user. The multiple pressure scores for eachuser could correspond to different categories of messages for a singleclient, where a user has a different pressure score for each category ofmessage. In that case, the pressure score for the user obtained in stepS404 would be the pressure score for the appropriate message category.

Where multiple pressure scores are maintained for each user, it isnecessary to determine which pressure score to use when making adetermination as to whether a message will be sent to a user. Thus, amethod embodying the invention may include an additional step where apressure category determining unit 308 of the pressure score unit 300checks the message to determine into which category the message belongs.Once that determination is made, then step S404 involves obtaining theuser's pressure score for that determined message category.

The description provided above explained that the categories of messagescould vary from client to client. In addition, the categories may relateto the type of message being sent. For example, a single user could havea first pressure score for push notifications, a second pressure scorefor text messages, a third pressure score for email messages, etc. Inthis situation, the pressure score obtained in step S404 would be theuser's pressure score for the type of message that is being sent.

Moreover, a single user that receives messages from multiple differentclients could have a different pressure score for each client, orperhaps multiple different pressure scores for each client. In thatevent, the pressure score that is obtained in step S404 would be thepressure score for the client that is sending the message, or perhapsthe pressure score for the appropriate category of message for theclient that is sending the message.

As will be explained in greater detail below, a message that is to besent to a user might also have an associated message threshold value.For example, a message that is determined to likely be of great interestto almost all users could be assigned a relative high message thresholdvalue. A message that is determined to be of little interest to manyusers may be assigned a low message threshold value.

When the message that is to be sent to users has an associated messagethreshold value, then in step S406 the user's pressure score is comparedto the message threshold value to determine if the user's pressure scoreis equal to or lower than the message threshold value. If a message hasa high message threshold value, indicating the message is likely to beinteresting to almost all users, then even users with a high pressurescore (indicating they are generally not receptive to new messages) willstill receive the message. If a message has a relative low messagethreshold value, indicating the message is not particularly interestingto most users, then the message will only be sent to those users with alow pressure score (indicating they are highly receptive to newmessages).

A method of maintaining a pressure score for a user will now bedescribed with references to the flowchart illustrated in FIG. 5. Inthis method, a single pressure score is maintained and updated for asingle user.

The method 500 begins and proceeds to step S502, where the messagesending unit 220 of a customer engagement service sends a message to auser. The method then proceeds to step S504, where a pressure scoremaintenance unit 302 of the pressure score unit 300 determines whetherthe user opens or views the message. As explained above, informationabout whether and when a user opens and views or listens to a messagecan be reported to the customer engage service 50 in a wide variety ofways. The message delivery service that was used to deliver the messagecould report this information. A client on behalf of whom the messagewas sent could report this information. A software application providedto a user by the client may report this information to the client, ordirectly to the customer engagement service. Alternatively, elements ofthe customer engagement service 50 itself may be capable of determiningwhether the user opens and/or views the message.

If the determination made in step S504 is that the user did not open orview or listen to the message, the method proceeds to step S506, wherethe pressure score for the user is increased. The method then loops backto step S502 and the steps described above repeat.

If the determination made in step S504 is that the user did open or viewor listen to the message, the method proceeds to step S506, where thepressure score for the user is decreased. The method then loops back tostep S502 and the steps described above repeat.

The method can proceed indefinitely, as more and more messages are sentto the user over time. The more often that a user opens/views messagessent to him, the lower the user's pressure score will become, indicatingthe user is highly receptive to new messages. The less frequently theuser opens/views messages, the higher the user's pressure score willbecome, indicating the user is not highly receptive to new messages.

In such a method, there may be a limit as to how much a user's pressurescore can be adjusted. For example, even if the user opens every messagethat is sent to him, the adjustments made in step S508 may not beallowed to adjust the user's pressure score below zero. Similarly, theremay be an upper bound for the user's pressure score.

In addition, a user's pressure score may be reset to a default orbaseline value, or to a desired value, for various reasons. This couldbe a manual adjustment made by a system administrator. Alternatively, auser's pressure score could be automatically reset on a periodic basis.

A user's activity or actions might also trigger an adjustment to theuser's pressure score. For example, if a user has a relatively highpressure score, and the user makes a purchase from the client, then thepurchase by the user might cause the user's pressure score to be reducedor reset to an initial value.

A user's pressure score might also be automatically reduced over time.For example, when a user's pressure score has become very high, the userwill receive few if any messages. However, the user's pressure scoremight be reduced by one point every day. When the pressure score becomessufficiently low, the user will once again begin receiving messages. Theend result would be that the user is given a break from messaging for acertain period of time, and then messaging resumes. This tactic might beeffective at reengaging the user.

A user's pressure score might also be treated differently than normalduring certain periods of time. For example, a new user may be treatedas having a low pressure score for X number of days after becoming a newuser, regardless of whether the user is opening and reading messages.Thereafter, the user's pressure score could be subject to the normaladjustment policies that are in effect.

If the customer engagement service 50 maintains multiple differentpressure scores for each user, the method described above could beindividually performed for each different type of pressure score.

In some embodiments, the determination made in step S504 may be timebounded. In other words, the question is not simply whether the userever opens or views the message, but instead whether the user opens orviews the message within a predetermined period of time after themessage was sent. If the user has not opened/viewed the message withinthe predetermined period of time, then after step S504 the methodproceeds to step S506 and the user's pressure score is increased.

In some embodiments of the invention, the determination made in stepS504 may be a multiple part question. For example, the question could bewhether the user opens/views a message within a first relatively shortpredetermined period of time after the message was sent, and if not,whether the user opens/views the message within a second, longerpredetermined period of time after the message was sent. If the useropens the message within the first short predetermined period of time,then step S508 could involve decreasing the user's pressure score by afirst relatively large amount. If the user opens the message within thesecond longer predetermined period of time, then in step S508 the user'spressure score would be reduced by a second smaller amount.

In a method as illustrated in FIG. 5, a single pressure score is beingmaintained and adjusted for a user. That does not mean that the userdoes not have other pressure scores that also are being maintained andadjusted, but rather that the method illustrated in FIG. 5 is onlyconcerned with maintaining one pressure score for the user.

In a method as illustrated in FIG. 5, the individual adjustments beingmade to the pressure score could vary in value or degree depending onthe type of message that was sent, or depending on the topic or subjectof the message, or for other reasons. For example, if the message sentin step S502 is a push notification, and in step S504 it is determinedthat the user opened and viewed the push notification, then in step S508the user's pressure score could be reduced by a first amount. However,if the message sent in step S502 is a text message, and in step S504 itis determined that the user opened and viewed the text message, then instep S508 the user's pressure score could be reduced by a second amountthat is different from the first amount. Similarly, the amount by whicha user's pressure score is adjusted in step S506 may vary depending ontype of the message, or the topic or subject of the message.

As mentioned above, messages may have an associated message thresholdvalue to which a user's pressure score is compared to determine if themessage should be sent to the user. FIG. 6 illustrates one method forassigning a message threshold value to a message.

The method 600 begins and proceeds to step S602, where a message is sentto a plurality of users. The message is one that will be sent to otherusers after a message threshold value has been established for themessage. Thus, the plurality of users to which the message is sent instep S602 are being used as part of a test to determine how interestingor valuable the message is likely to be to users.

The method then proceeds to step S604, where a message threshold valuedetermining unit 306 of the pressure score unit 300 determines how manyof the plurality of users opened or viewed the message. As noted above,this information can be reported to the customer engagement service 50in a variety of ways, or the customer engagement service 50 may itselfbe capable of making this determination for some or all of the pluralityof users.

In step S606, the message threshold value determining unit 306determines a message threshold value for the message based on the resultof the determination in step S604. If the majority of the plurality ofusers opened/viewed the message, that would indicate that the message isquite interesting to users. In that case, in step S606 the message isassigned a relatively high message threshold value. As a result, themessage will be sent, in a method as illustrated in FIG. 4, to mostusers, even to those users that have a high pressure score. On the otherhand, if the message is not opened/viewed by most of the plurality ofusers, in step S606 the message is assigned a relatively low pressurescore. As a result, a method as illustrated in FIG. 4 would end upsending the message only to those users with a relatively low pressurescore. The method then ends.

In some embodiments, the determination made in step S604 is timebounded. In other words, step S604 involves determining how many of theplurality of users opened/viewed the message within a predeterminedperiod of time after the message was sent. If the message is quicklyopened or viewed by a certain percentage of the plurality of users, thenstep S606 could involve assigning a relatively high message thresholdvalue, indicating the message was quite interesting.

The determination made in step S606 could depend on multiple factors.The message threshold value could be set based on the percentage of theplurality of users that view the message within a predetermined periodof time, as well as the percentage to the plurality of users that viewthe message before a cutoff time.

In some embodiments, the plurality of users to which the message is sentwould be randomly selected. This would help to ensure that the messagethreshold value assigned to the message is likely representative of theaverage degree to which all users will find the message interesting orvaluable.

In alternate methods, the plurality of users to which the message issent may be deliberately selected to achieve certain analysis goals. Forexample, the plurality of users could be those users who already have ahigh pressure score for the type of message being sent. As a result, ifa large number of the plurality of users open/view the message, it wouldbe strong evidence that the message is quite interesting or valuable tousers.

Conversely, the plurality of users may be users that have a relativelylow pressure score for the type of message being sent. If a large numberof those users fail to open/view the message, it would be strongevidence that the message is of very little interest or value to users.

A pressure score as described above might also be used in other ways toassist the customer engagement service in accomplishing its goals. Oneway relates to the delivery of email messages.

As noted above, the email messages that are sent by the clientengagement service 50 to the users may be delivered by third party emailservices. Such third party email services employ various tactics toprevent or eliminate the delivery of SPAM messages. For example, when athird party email service receives for delivery a large number of highlysimilar messages, the email service may send only a first portion of themessages to the indicated users. The email service then waits to see ifthose messages are ignored by the users to which they were delivered, tosee if they are moved into SPAM folders, and to see if users delete themessage without reading it. If those types of activities occur for alarge percentage of the messages from the first block that was sent tousers, the email service may decide the messages likely are SPAM, inwhich case the email service may refuse to deliver the remainingmessages. On the other hand, if a relatively large percentage of theusers to which the first block of email messages was sent open and readthe message, the email service may determine that the message islegitimate, and the email service will then send the remaining messageson to the addressed users.

In view of the SPAM reduction practices employed by email services, thecustomer engagement service 50 can use the pressure scores of the usersto identify those users that are most likely to open or read emailmessages—those being the users with low pressure scores. When thecustomer engagement service 50 is tasked by a client with delivering anemail message to the client's users, the customer engagement service 50could send a first block of email messages to those users with a lowpressure score. Because users with a low pressure score havedemonstrated that they are receptive to messages, the users will likelyopen and read the email message. This will signal to the email servicethat the message is not likely SPAM. As a result, the email service isunlikely to block the email message when the customer engagement service50 thereafter sends the same email message to other users with higherpressure scores.

Pressure scores might also be used to test various different versions ofa message in an attempt to determine which version of the message ismost likely to be interesting or engaging to users. For example, if aclient has tasked the customer engagement service 50 with sending amessage to the client's users, the customer engagement service 50 couldcreate several different versions of the message that all includeessentially the same content. The subject line of the message could bedifferent in each of the different versions. Also, the content of themessage could be slightly varied in the various different versions. Eachof the versions could be sent to a different group of users, all ofwhich have a relative high pressure score, indicating they generally arenot receptive to new messages. If one of the version of the message isread by a relative high percentage of the group of users to which it wassent, this would indicate that the version sent to that group isparticularly interesting or engaging. That version of the message couldthen be sent to all other users. Operating in this fashion would likelyresult in the largest number of users opening and reading the message.

Conversely, the customer engagement service 50 could send differentversions of a message first to different groups of users with relativelylow pressure scores to see which of the versions has the highestengagement factor with users. Only the version(s) with the highestengagement factor would thereafter be sent to users with a relative highpressure score. Operating in this fashion might avoid irritating theusers with high pressure scores, while still obtaining information aboutwhich of the versions appears to most interesting or engaging to users.

Pressure scores might also be used to control or determine the deliverychannel for a message. Many users view push notifications as somewhatinvasive, whereas users view email messages or in-app messages as lessinvasive. Thus, the customer engagement service 50 could send aparticular message via a push notification to those users who have a lowpressure score, indicating they are relative receptive to new messages.The same message could be sent to users with a high pressure score as anemail message or an in-app message. Thus, a user's pressure score couldbe used to select the delivery channel through which a message is sentto the user.

The present invention may be embodied in methods, apparatus, electronicdevices, and/or computer program products. Accordingly, the inventionmay be embodied in hardware and/or in software (including firmware,resident software, micro-code, and the like), which may be generallyreferred to herein as a “circuit” or “module.” Furthermore, the presentinvention may take the form of a computer program product on acomputer-usable or computer-readable storage medium havingcomputer-usable or computer-readable program code embodied in the mediumfor use by or in connection with an instruction execution system. In thecontext of this document, a computer-usable or computer-readable mediummay be any medium that can contain, store, communicate, propagate, ortransport the program for use by or in connection with the instructionexecution system, apparatus, or device. These computer programinstructions may also be stored in a computer-usable orcomputer-readable memory that may direct a computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer-usable orcomputer-readable memory produce an article of manufacture includinginstructions that implement the function specified in the flowchartand/or block diagram block or blocks.

The computer-usable or computer-readable medium may be, for example butnot limited to, an electronic, magnetic, optical, electromagnetic,infrared, or semiconductor system, apparatus or device. More specificexamples (a non-exhaustive list) of the computer-readable medium includethe following: hard disks, optical storage devices, magnetic storagedevices, an electrical connection having one or more wires, a portablecomputer diskette, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, and a compact disc read-only memory (CD-ROM).

Computer program code for carrying out operations of the presentinvention may be written in an object oriented programming language,such as Java®, Smalltalk or C++, and the like. However, the computerprogram code for carrying out operations of the present invention mayalso be written in conventional procedural programming languages, suchas the “C” programming language and/or any other lower level assemblerlanguages. It will be further appreciated that the functionality of anyor all of the program modules may also be implemented using discretehardware components, one or more Application Specific IntegratedCircuits (ASICs), or programmed Digital Signal Processors ormicrocontrollers.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the present disclosure and its practical applications, tothereby enable others skilled in the art to best utilize the inventionand various embodiments with various modifications as may be suited tothe particular use contemplated.

FIG. 7 depicts a computer system 700 that can be utilized in variousembodiments of the present invention to implement the inventionaccording to one or more embodiments. The various embodiments asdescribed herein may be executed on one or more computer systems, whichmay interact with various other devices. One such computer system is thecomputer system 700 illustrated in FIG. 7. The computer system 700 maybe configured to implement the methods described above. The computersystem 700 may be used to implement any other system, device, element,functionality or method of the above-described embodiments. In theillustrated embodiments, the computer system 700 may be configured toimplement the disclosed methods as processor-executable executableprogram instructions 722 (e.g., program instructions executable byprocessor(s) 710) in various embodiments.

In the illustrated embodiment, computer system 700 includes one or moreprocessors 710 a-710 n coupled to a system memory 720 via aninput/output (I/O) interface 730. Computer system 700 further includes anetwork interface 740 coupled to I/O interface 730, and one or moreinput/output devices 750, such as cursor control device 760, keyboard770, display(s) 780, microphone 782 and speakers 784. In variousembodiments, any of the components may be utilized by the system toreceive user input described above. In various embodiments, a userinterface may be generated and displayed on display 780. In some cases,it is contemplated that embodiments may be implemented using a singleinstance of computer system 700, while in other embodiments multiplesuch systems, or multiple nodes making up computer system 700, may beconfigured to host different portions or instances of variousembodiments. For example, in one embodiment some elements may beimplemented via one or more nodes of computer system 700 that aredistinct from those nodes implementing other elements. In anotherexample, multiple nodes may implement computer system 700 in adistributed manner.

In different embodiments, the computer system 700 may be any of varioustypes of devices, including, but not limited to, a personal computersystem, desktop computer, laptop, notebook, or netbook computer, aportable computing device, a mainframe computer system, handheldcomputer, workstation, network computer, a smartphone, a camera, a settop box, a mobile device, a consumer device, video game console,handheld video game device, application server, storage device, aperipheral device such as a switch, modem, router, or in general anytype of computing or electronic device.

In various embodiments, the computer system 700 may be a uniprocessorsystem including one processor 710, or a multiprocessor system includingseveral processors 710 (e.g., two, four, eight, or another suitablenumber). Processors 710 may be any suitable processor capable ofexecuting instructions. For example, in various embodiments processors710 may be general-purpose or embedded processors implementing any of avariety of instruction set architectures (ISAs). In multiprocessorsystems, each of processors 710 may commonly, but not necessarily,implement the same ISA.

System memory 720 may be configured to store program instructions 722and/or data 732 accessible by processor 710. In various embodiments,system memory 720 may be implemented using any suitable memorytechnology, such as static random access memory (SRAM), synchronousdynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type ofmemory. In the illustrated embodiment, program instructions and dataimplementing any of the elements of the embodiments described above maybe stored within system memory 720. In other embodiments, programinstructions and/or data may be received, sent or stored upon differenttypes of computer-accessible media or on similar media separate fromsystem memory 720 or computer system 700.

In one embodiment, I/O interface 730 may be configured to coordinate I/Otraffic between processor 710, system memory 720, and any peripheraldevices in the device, including network interface 740 or otherperipheral interfaces, such as input/output devices 750. In someembodiments, I/O interface 730 may perform any necessary protocol,timing or other data transformations to convert data signals from onecomponent (e.g., system memory 720) into a format suitable for use byanother component (e.g., processor 710). In some embodiments, I/Ointerface 730 may include support for devices attached through varioustypes of peripheral buses, such as a variant of the Peripheral ComponentInterconnect (PCI) bus standard or the Universal Serial Bus (USB)standard, for example. In some embodiments, the function of I/Ointerface 730 may be split into two or more separate components, such asa north bridge and a south bridge, for example. Also, in someembodiments some or all of the functionality of I/O interface 730, suchas an interface to system memory 720, may be incorporated directly intoprocessor 710.

Network interface 740 may be configured to allow data to be exchangedbetween computer system 700 and other devices attached to a network(e.g., network 790), such as one or more external systems or betweennodes of computer system 700. In various embodiments, network 790 mayinclude one or more networks including but not limited to Local AreaNetworks (LANs) (e.g., an Ethernet or corporate network), Wide AreaNetworks (WANs) (e.g., the Internet), wireless data networks, some otherelectronic data network, or some combination thereof. In variousembodiments, network interface 740 may support communication via wiredor wireless general data networks, such as any suitable type of Ethernetnetwork; for example, via telecommunications/telephony networks such asanalog voice networks or digital fiber communications networks, viastorage area networks such as Fiber Channel SANs, or via any othersuitable type of network and/or protocol.

Input/output devices 750 may, in some embodiments, include one or moredisplay terminals, keyboards, keypads, touchpads, scanning devices,voice or optical recognition devices, or any other devices suitable forentering or accessing data by one or more computer systems 700. Multipleinput/output devices 750 may be present in computer system 700 or may bedistributed on various nodes of computer system 700. In someembodiments, similar input/output devices may be separate from computersystem 700 and may interact with one or more nodes of computer system700 through a wired or wireless connection, such as over networkinterface 740.

In some embodiments, the illustrated computer system may implement anyof the operations and methods described above, such as the methodsillustrated by the flowcharts of FIGS. 4-6. In other embodiments,different elements and data may be included.

Those skilled in the art will appreciate that the computer system 700 ismerely illustrative and is not intended to limit the scope ofembodiments. In particular, the computer system and devices may includeany combination of hardware or software that can perform the indicatedfunctions of various embodiments, including computers, network devices,Internet appliances, PDAs, wireless phones, pagers, and the like.Computer system 700 may also be connected to other devices that are notillustrated, or instead may operate as a stand-alone system. Inaddition, the functionality provided by the illustrated components mayin some embodiments be combined in fewer components or distributed inadditional components. Similarly, in some embodiments, the functionalityof some of the illustrated components may not be provided and/or otheradditional functionality may be available.

Those skilled in the art will also appreciate that, while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from computer system 700 may be transmitted to computer system700 via transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as a network and/or a wireless link. Various embodiments mayfurther include receiving, sending or storing instructions and/or dataimplemented in accordance with the foregoing description upon acomputer-accessible medium or via a communication medium. In general, acomputer-accessible medium may include a storage medium or memory mediumsuch as magnetic or optical media, e.g., disk or DVD/CD-ROM, volatile ornonvolatile media such as RAM (e.g., SDRAM, DDR, RDRAM, SRAM, and thelike), ROM, and the like.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

While the invention has been described in connection with what ispresently considered to be the most practical and preferred embodiment,it is to be understood that the invention is not to be limited to thedisclosed embodiment, but on the contrary, is intended to cover variousmodifications and equivalent arrangements included within the spirit andscope of the appended claims.

What is claimed is:
 1. A computer implemented method of sending amessage to a user, comprising: receiving a message that is to be sent toa user; obtaining a pressure score for the user that is indicative ofhow receptive the user is to receiving messages in general, regardlessof the topic of the messages; determining, based on at least the user'sobtained pressure score, whether the message should be sent to the user;and sending the message to the user when it is determined that themessage should be sent to the user.
 2. The method of claim 1, whereindetermining whether the message should be sent to the user comprisesdetermining whether the user's pressure score is equal to or below athreshold value.
 3. The method of claim 1, wherein determining whetherthe message should be sent to the user comprises determining whether theuser's pressure score is equal to or below a message threshold valueassociated with the message.
 4. The method of claim 3, wherein themessage threshold value associated with the message is based upon howengaging or interesting the message was to other users.
 5. The method ofclaim 3, wherein the message threshold value is representative of apercentage of other users that received the message and then opened orviewed the message.
 6. The method of claim 1, wherein the receivedmessage includes an indication of a topic or subject or the message,wherein obtaining a pressure score for the user further comprisesobtaining a topical pressure score for the user that is indicative ofhow receptive the user is to receiving messages that are directed to thetopic or subject of the message, and wherein the determination ofwhether the message should be sent to the user is based, at least inpart, on the obtained topical pressure score for the user.
 7. The methodof claim 1, wherein the received message is of a certain type, whereinobtaining a pressure score for the user further comprises obtaining atype pressure score for the user that is indicative of how receptive theuser is to receiving messages of the type of the received message, andwherein the determination of whether the message should be sent to theuser is based, at least in part, on the obtained type pressure score forthe user.
 8. A system for sending a message to a user, comprising: amessage sending unit comprising at least one processor that isconfigured to receive a message that is to be sent to a user; a pressurescore unit comprising at least one processor that is configured toobtain a pressure score for the user that is indicative of how receptivethe user is to receiving messages in general, regardless of the topic ofthe messages, and to determine, based on at least the user's obtainedpressure score, whether the message should be sent to the user; whereinthe message sending unit sends the message to the user when the pressurescore unit determines that the message should be sent to the user. 9.The system of claim 8, wherein the pressure score unit compares theuser's pressure score to a threshold value and determines that themessage should be sent to the user when the user's pressure score isequal to or below the threshold value.
 10. The system of claim 8,wherein the pressure score unit compares the user's pressure score to amessage threshold value associated with the message and determines thatthe message should be sent to the user when the user's pressure score isequal to or below the message threshold value.
 11. The system of claim10, wherein the message threshold value associated with the message isbased upon how engaging or interesting the message was to other users.12. The system of claim 10, wherein the message threshold value isrepresentative of a percentage of other users that received the messageand then opened or viewed the message.
 13. The system of claim 8,wherein the received message includes an indication of a topic orsubject or the message, wherein the pressure score unit also obtains atopical pressure score for the user that is indicative of how receptivethe user is to receiving messages that are directed to the topic orsubject of the message, wherein the pressure score unit compares theobtained topical pressure score for the user to a threshold value anddetermines that the message should be sent to the user when the user'stopical pressure score is equal to or below the threshold value.
 14. Thesystem of claim 8, wherein the received message is of a certain type,wherein the pressure score unit also obtains a type pressure score forthe user that is indicative of how receptive the user is to receivingmessages of the type of the received message, wherein the pressure scoreunit compares the obtained type pressure score for the user to athreshold value and determines that the message should be sent to theuser when the user's type pressure score is equal to or below thethreshold value.